Currently, there are two LocalLifecycleOwner in cmp 1.6.10 (1.7.0+ will resolved it):

• androidx.compose.ui.platform.LocalLifecycleOwner
• androidx.lifecycle.compose.LocalLifecycleOwner

As per jetbrains's suggestion:

// androidx.lifecycle.compose.LocalLifecycleOwner.kt
Note: On Android, it works only with Compose UI 1.7.0-alpha05 or above.
 *  Please use [androidx.compose.ui.platform.LocalLifecycleOwner] on Compose 1.6.*

In the cmp code, wo can find that two LocalLifecycleOwner are the same without androidTarget.

skiko:

// TODO: Deprecate in 1.7.0
// @Deprecated(
//    "Moved to lifecycle-runtime-compose library in androidx.lifecycle.compose package.",
//    ReplaceWith("androidx.lifecycle.compose.LocalLifecycleOwner"),
// )
actual val LocalLifecycleOwner get() = androidx.lifecycle.compose.LocalLifecycleOwner

androidTarget:

actual val LocalLifecycleOwner = staticCompositionLocalOf<LifecycleOwner> {
    noLocalProvidedFor("LocalLifecycleOwner")
}

For now there are a lot of projects that are starting to use jetbrains-lifecycle-runtime-compose, I suggest we can provide androidx.lifecycle.compose.LocalLifecycleOwner in androidTarget first, and then provide the only androidx.lifecycle.compose.LocalLifecycleOwner in commonMain after cmp 1.7.0, this ensures that the user's normal use is guaranteed.